(In reply to Kris Maglione [:kmag] from comment #3) > (In reply to Nick Alexander :nalexander [he/him] from comment #2) > > kmag: hello! Before implementing something, I'd like to get some feedback from you. What I want to do is add a "background task mode" to Firefox, so that when you run `firefox --backgroundtask FOO` the XPCOM graph and category registrations can depend on the specified background task. > > I'm OK with the general idea, but I'd rather we only add support to the new static XPCOM manifest system and not to old-style `chrome.manifest` files. I'd rather not encourage people to use the latter for new code. Ideally I'd like to remove support for them at some point. Understood, but there's a good deal of category registration that I need to disable for my immediate use case. I don't think we can commit to completing the transition to static components for this particular project. > > ``` > > 'categories': { > > 'command-line-handler': { > > 'category': 'm-browser', > > Nit: this should be something like `'name'` or `'entryName'`, not `'category'`. The category, in this case, would be `command-line-handler`, and `m-browser` would be the name of this entry. Roger that. I'll knock something up and have you review it. Thanks for the snappy rely, Kris!
Bug 1675848 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Kris Maglione [:kmag] from comment #3) > (In reply to Nick Alexander :nalexander [he/him] from comment #2) > > kmag: hello! Before implementing something, I'd like to get some feedback from you. What I want to do is add a "background task mode" to Firefox, so that when you run `firefox --backgroundtask FOO` the XPCOM graph and category registrations can depend on the specified background task. > > I'm OK with the general idea, but I'd rather we only add support to the new static XPCOM manifest system and not to old-style `chrome.manifest` files. I'd rather not encourage people to use the latter for new code. Ideally I'd like to remove support for them at some point. Understood, but there's a good deal of category registration that I need to disable for my immediate use case. I don't think we can commit to completing the transition to static components for this particular project. > > ``` > > 'categories': { > > 'command-line-handler': { > > 'category': 'm-browser', > > Nit: this should be something like `'name'` or `'entryName'`, not `'category'`. The category, in this case, would be `command-line-handler`, and `m-browser` would be the name of this entry. Roger that. I'll knock something up and have you review it. Thanks for the snappy reply, Kris!